home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
os2
/
pine394.zip
/
README.OS2
Wrap
Text File
|
1996-06-26
|
5KB
|
127 lines
-------------------------------------------------------------
This is Pine for OS/2, a text mode IMAP-capable mail and news
client for 32-bit OS/2, including OS/2 version 2.0 and later.
-------------------------------------------------------------
This version of Pine is a network client, and requires you to
have IBM TCP/IP 2.0 or later installed. The OS/2 Warp IAK is
sufficient to run this program across either a SLIP or PPP
link.
Note on mailboxes: The default mailbox type uses the IMAP
v2bis protocol. To use IMAP, you will need to be connecting
to a mail server with an IMAP server that supports IMAP
version 2 or later. Pine may also be used with POP v2 or v3
servers, but is not as functional by a large margin.
To define an IMAP mailbox, you enter the following:
{your.mail.server.fdqn}INBOX for your standard mailbox
{your.mail.server.fdqn}path/folder for other mail folders
To define a POP3 style mailbox, you enter:
{your.mail.servers.fdqn/pop3}INBOX
Note that POP only supports one mailbox on your server - that
is the standard mailbox for incoming mail.
This version of Pine uses smtp delivery only, and is not
suitable for an OS/2 system set up as a mail server. That
would require a great many changes to the c-client system
(for OS/2, at least).
Local mail folders created and maintained by PineOS2 are in
"dawz" format, which is identical to the format used by the
MSDOS and Windows builds of Pine. This version of Pine is
also able to read "Berkeley" style mail folders, but only in
read- only mode. Since you can copy between folders using the
S)ave command from the mail folder index, you can move mail
freely from Berkeley format mail folders to dawz, but not the
reverse.
If you wish to log in automatically to your server without
having to specify a login name or password each time, create
an empty file called "PINE.PWD" in the same directory where
Pine creates its PINERC configuration file.
Before running Pine, set either the HOME environment
variable, or the PINEHOME variable (if you have other
software that uses HOME but wish to place Pine elsewhere) in
your CONFIG.SYS - and remember to reboot.
Files in the "bin" subdirectory should be placed somewhere in
your PATH. Files in the "dll" subdirectory should be placed
in a directory that is specified in your LIBPATH setting.
Files under the "emx" subdirectory should also be placed into
a directory in your LIBPATH, but check first to ensure that
there are no other files of the same name on your system.
These files come from the EMX runtime version 0.9b, and you
will need these or the equivalent later versions to run Pine
without problems.
For the convenience of WPS users, this version of Pine
includes a -w <lines> command line switch which sets the
window size by the number number of lines to which Pine
should set Vio window. The INSTPINE.CMD supplied simply
creates an object on your desktop a some typical setting
and allows you to select the standard desktop size you wish
to use. You can change this on the fly by a shell to the
prompt via ^Z (assuming this has been enabled), using the
"mode" command to set the number of lines, then "exit" back
to Pine.
When you run INSTPINE.CMD, you must be in the same directory
as pine.exe.
Sample scripts are provided as a sample of how you might
configure Pine to automatically sign messages with PGP,
and verify signatures on incoming messages so signed.
You need to have PGP installed correctly with a valid
secret and/or public keyring on your system before these
scripts will be of any use.
The "misc" subdirectory contains a program called "addff"
which may be configured as a filter via the Custom Printer
to add a formfeed after all output is done (Pine's internal
"formfeed" setting only adds a formfeed BETWEEN messages,
but does not add one at the end). Read the comments in
the .c source file for program use.
-----
Please read the documentation carefully before email the
porter for technical support, and do so only as a last
resort. Due to many other committements, at this I am not
able to guarantee prompt response to email. Bug reports, on
the other hand, are always welcome.
OS/2 Port: David Nugent
Email: davidn@blaze.net.au
FidoNet: 3:632/348@fidonet
-- BUILDING PINE --
The port to OS/2 has been incorprated into the standard
Pine source distribution, which can be found at
ftp://ftp.cac.washington.edu/pine/pine3.94.tar.gz.
Before building PineOS2, you will need:
emx 0.9b development system and gcc 2.7.2 or later
gnu make
gnu shell utilities or functional equivalents (cp,rm,mv)
All can be obtained from the OS/2 archives at hobbes.nmsu.edu.
You will also need to convert the files build.cmd in the
Pine source root directory and imap\ANSI\c-client\drivers.cmd
from "UNIX" newline delimited files to standard DOS CRLF
files so that IBM REXX will be able to read them
correctly. Other than that, just type 'build' and that should
build Pine for OS2 with no further action necessary.